chore(examples): add TransactionBuilder publish and upgrade example
#271
Conversation
Alex6323
changed the title
TransactionBuilder upgrade exampleTransactionBuilder publish and upgrade example
| } | ||
|
|
||
| // Compiled `first_package` example | ||
| const SERIALIZED_FIRST_PACKAGE: &str = r#"{"modules":["oRzrCwYAAAAKAQAIAggUAxw+BFoGBWBBB6EBwQEI4gJACqIDGgy8A5cBDdMEBgAKAQ0BEwEUAAIMAAABCAAAAAgAAQQEAAMDAgAACAABAAAJAgMAABACAwAAEgQDAAAMBQYAAAYHAQAAEQgBAAAFCQoAAQsACwACDg8BAQwCEw8BAQgDDwwNAAoOCgYJBgEHCAQAAQYIAAEDAQYIAQQHCAEDAwcIBAEIAAQDAwUHCAQDCAAFBwgEAgMHCAQBCAIBCAMBBggEAQUBCAECCQAFBkNvbmZpZwVGb3JnZQVTd29yZAlUeENvbnRleHQDVUlEDWNyZWF0ZV9jb25maWcMY3JlYXRlX3N3b3JkAmlkBGluaXQFbWFnaWMJbXlfbW9kdWxlA25ldwluZXdfc3dvcmQGb2JqZWN0D3B1YmxpY190cmFuc2ZlcgZzZW5kZXIIc3RyZW5ndGgOc3dvcmRfdHJhbnNmZXIOc3dvcmRzX2NyZWF0ZWQIdHJhbnNmZXIKdHhfY29udGV4dAV2YWx1ZQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAgMHCAMJAxADAQICBwgDEgMCAgIHCAMVAwAAAAABCQoAEQgGAAAAAAAAAAASAQsALhELOAACAQEAAAEECwAQABQCAgEAAAEECwAQARQCAwEAAAEECwAQAhQCBAEAAAEOCgAQAhQGAQAAAAAAAAAWCwAPAhULAxEICwELAhIAAgUBAAABCAsDEQgLAAsBEgALAjgBAgYBAAABBAsACwE4AgIHAQAAAQULAREICwASAgIAAQACAQEA"],"dependencies":["0x0000000000000000000000000000000000000000000000000000000000000002","0x0000000000000000000000000000000000000000000000000000000000000001"],"digest":[246,127,102,77,186,19,68,12,161,181,56,248,210,0,91,211,245,251,165,152,0,197,250,135,171,37,177,240,133,76,122,124]}"#; |
There was a problem hiding this comment.
I would say either move this to a fixture or just compile it using the iota binary in the example.
There was a problem hiding this comment.
I think the examples need to be copy and paste friendly and self-contained, but if we move this out, then it has some dependency on the environment.
There was a problem hiding this comment.
Hmm. But this example necessarily involves an external package, so maybe it should be an exception
There was a problem hiding this comment.
not entirely sure I understand what you mean ... the original example can now evolve separately without us to ever have to consider it again. So we aren't dependent on it anymore? And what you suggested in your first message (compiling it) is what I did, no? This is the compiled output of that package, just serialized as json/base64 using the iota CLI.
There was a problem hiding this comment.
I meant compiling it in the example by calling iota move build
| return id | ||
| }(), | ||
| } | ||
| compiledPackageDigest := []byte{246, 127, 102, 77, 186, 19, 68, 12, 161, 181, 56, 248, 210, 0, 91, 211, 245, 251, 165, 152, 0, 197, 250, 135, 171, 37, 177, 240, 133, 76, 122, 124} |
There was a problem hiding this comment.
Can we do a Digest::from_base58 here?
There was a problem hiding this comment.
@Thoralf-M do you want to continue with the bindings?
I realized during the Rust example that it's probably better for the end-user to merge the |
| fmt.Printf("Effects status (upgrade): %s\n", (*effects2).AsV1().Status) | ||
|
|
||
| // Wait some time for the indexer to process the tx | ||
| time.Sleep(10 * time.Second) |
There was a problem hiding this comment.
I forgot to revert the time here, 3 seconds should be enough
4 participants
Closes #228
Closes #229